home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
pc_board
/
pcbfre25.zip
/
PCBFRE.DOC
< prev
next >
Wrap
Text File
|
1992-05-07
|
42KB
|
1,034 lines
PCBFRE
PCBoard Dynamic File Ratio Enforcer
A PCBoard Post/Call Ratio Enforcer
Post/Download Ratio Enforcer
Files Ratio Enforcer
Bytes Ratio Enforcer
Time/Byte Bank
Bytes Per Message Reward
Version 2.2 (07-May-1992)
PCBFRE22.ZIP
For use with PCBoard Versions 14.5+
Copyright 1991, 1992 Geoffrey Sy
ALL RIGHTS RESERVED
This program is supported by:
Geoffrey Sy
51 Wyatt Walk
Toronto, Ontario Canada
M5A 3T3
Support BBS:
The GRAFIX Connection
HST: (416) 287-9002
2400: (416) 286-8734
Best time to call: 5:30 - 9:00 am E.S.T.
┌────────────────────────────────────────────────────────────────┐
│ TABLE OF CONTENTS │
└────────────────────────────────────────────────────────────────┘
Introduction .................................................... 3
Installation .................................................... 3
Edit PCBoard's PWRD ........................................ 3
Using FRESM ................................................ 3
Edit PCBFRE's Configuration ................................ 4
Edit PCBFRE Ratio table .................................... 5
The Ratio System Examples .................................. 6
Edit Bank Limits ........................................... 7
Edit PCBoard's Door Security File .......................... 7
Edit PCBFRE Door Script file ............................... 8
PCBFRE Command line options ................................ 8
Trial Run .................................................. 9
Edit FRETEXT ............................................... 9
PCBFRE's Display Files ................................. 4, 10
PCBFRE Display Files Substitution Variables ............... 10
PCBFRE banking features ................................... 12
Program Capabilities............................................ 13
Security/Language specific display files .................. 13
Non-Standard COM Ports .................................... 13
Session Logging ........................................... 13
Multi-Tasking/Node Support ................................ 13
Network, File Sharing Support ............................. 13
SysOp Function Keys ....................................... 14
Error Codes ................................................ 14, 15
Problem Report Procedure .................................. 15
Support/Registrations........................................... 16
Disclaimers/Copyrights/Credits ................................. 17
─────────────────────────────────────────────────────────────────
PCBoard File Ratio Enforcer v2.0 . . . . . . . . . . . . . . . 2
┌────────────────────────────────────────────────────────────────┐
│ INTRODUCTION │
└────────────────────────────────────────────────────────────────┘
PCB File Ratio Enforcer was created to compliment PCBoard's lack of
ratio enforcement. PCBFRE is a door for PCBoard 14.5+ to enforce
the available download bytes based on download/upload, post/call,
post/download ratios. Some enhanced features include bytes reward
for message posts and a unique time/byte banking system.
┌────────────────────────────────────────────────────────────────┐
│ PROGRAM INSTALLATION/OPERATION │
└────────────────────────────────────────────────────────────────┘
Step #1:
=======
Edit PCBoard's PWRD file and set daily download bytes to 0 for the
security levels to be enforced with PCBFRE. This step is required
to stop PCBoard from giving the user any bytes. When PCBFRE is
used, PCBFRE calculates the amount of bytes the user is allowed to
receive based on his ratios.
Step #2:
========
Edit PCBFRE's configuration file. The one included in this archive
is called PCBFRE.CNF. Please use FRESM to edit this file. The
command line for starting FRESM is:
FRESM PCBFRE.CNF C:\PCB
│ │
│ └┤ PCBoard System directory
│
└─────────┤ Name of CNF file
FRESM will create a configuration file if one does not already
exist. The location of your PCBoard Systems directory is required
for FRESM to obtain the colour and text editor configuration from
PCBSM.CNF and PCBSM.CLR.
There are 3 options on the main menu:
A - Edit Configuration File
B - Edit PCBFRE Security Table
C - Edit Banking Data File
─────────────────────────────────────────────────────────────────
PCBoard File Ratio Enforcer v2.0 . . . . . . . . . . . . . . . 3
Option A: Edits PCBFRE's configuration file options.
1. ║ BBS Name: Simple Solutions Software
2. ║ Registration # 0
║
3. ║ Use slow BIOS comm driver (Y/N): N
║
4. ║ NORMAL display file : NORMAL
5. ║ FILES/BYTES EXCEEDED display file: FILES
6. ║ MESSAGE EXCEEDED display file : MSGS
7. ║ RATIO NOT ENFORCED display file : EXEMPT
║
8. ║ FRE Bank Welcome display file : WELCOME
9. ║ FRE Bank Goodbye display file : GOODBYE
10. ║ FRE Bank Help display file : HELP
11. ║ FRE Bank Menu display file : MENU
1. This is where you enter your BBS name. If you have
registered PCBFRE, this must be the same as the BBS name
entered in PCBoard.
2. The registration code you receive when you register
PCBFRE.
3. This tells PCBFRE how to communicate with your modem.
Older PCs and not 99%+ MS-DOS compatible machines such as
Tandy and alike may need to set this to Y. The setting
for the majority of PCs is N. If one setting doesn't
work on your PC, the other might.
4. This text file will be displayed when the user's ratio is
within normal limit.
5. This text file will be displayed when the user's files or
bytes ratio has been exceeded.
6. This text file will be displayed when the user's messages
ratio has been exceeded.
7. This text file will be displayed when the user's ratios
are not being enforced by PCBFRE.
8. This file will be displayed when the user enters the
bank.
9. This file will be displayed when the user exits the bank.
10. This file explains the commands in the bank. The '?' or
'H' command will display it.
11. The list of commands and short explanations for the bank.
─────────────────────────────────────────────────────────────────
PCBoard File Ratio Enforcer v2.0 . . . . . . . . . . . . . . . 4
Option B:
--------
This option edits PCBFRE's Security levels table. This is where
the ratio options for the security levels are controlled.
1. ║ Security Level ....... 60
2. ║ Bytes Ratio .......... 3.00
3. ║ Files Ratio .......... 4.00
4. ║ Message Ratio ........ 7.00
5. 6.║ Maximum Daily Limit .. 204800 Enforce Daily (Y/N)? N
7. ║ Base Baud Rate ....... 0
8. 9.║ Bytes per Message .... 1024 Enforce Daily (Y/N)? N
10. ║ Bank Daily Time Limit ...... 30
11. ║ Bank Maximum Time Bal ...... 60
12. ║ Bank Daily Bytes Limit ..... 102400
1. The security level to be enforced.
2. The number of bytes the user may download for each byte
uploaded.
3. The number of file the user may download for each file
uploaded.
4. The number of calls or downloads the user may make for
each message left.
5. The maximum byte limit the user may download per session.
Set it to 0 if you don't want the user to download.
6. When this is set to Y, the maximum limit (item 5) is
only calculated on the first call.
7. Similar to PCBoard's base baud rate setting. When set,
the maximum daily limit will be adjusted according to the
user's connect baud rate.
8. The number of bytes given to the user for each message
post.
9. This setting decides when to reward the message posts.
When set to Y PCBFRE will only reward the user once per
day. When the N setting is used, the bytes are rewarded
every time PCBFRE detects a new message post.
10. The number of minutes the user may withdraw per day.
11. Then maximum number of minutes allowed in the account.
12. The number of bytes the user may withdraw per day.
─────────────────────────────────────────────────────────────────
PCBoard File Ratio Enforcer v2.0 . . . . . . . . . . . . . . . 5
┌────────────────────────────────────────────────────────────────┐
│ THE RATIO SYSTEM │
└────────────────────────────────────────────────────────────────┘
The illustration on the previous page translates to the following:
Bytes ratio: 3:1 Files ratio: 4:1
Messages ratio: 7:1
Session limit: 200K
BPM reward: 1K
Bank balance limit: 60 minutes
Bank daily limit: 30 minutes
Bytes withdrawal limit: 100K
Users with security level 60 may download 3 bytes for each
byte they upload up to a maximum of 200K per session. For
every 4 files they download they must upload one file. They
must post 1 message every 7 calls and are given 1K for each
message they post. All ratios and rewards are recalculated
each time PCBFRE is executed. Baud rate is not taken into
account.
Let's take a look at another example. This one is for those SysOps
who value message participation than files:
Bytes ratio: 1:1 Files ratio: 0:0
Messages ratio: 1:1
Session limit: 200K
BPM reward: 5K
Users are required to upload 1 byte for each byte they
download up to a maximum of 200K per session. They must post
a message each call and are given 5K for each message post.
If the 1:1 post/call ratio system cause the phone line to be
free all the time, the post/download ratio system may be the
answer. Use the command line switch /POSTDL to enable this.
For BBSes where bytes don't count much, such as systems specialized
in game cheats, un-protects, docs:
Bytes ratio: 0:0 Files ratio: 1:1
Messages ratio: 0:0
Session limit: 100K
Users are required to upload one file for each one downloaded.
After every 100K downloads, they must recalculate their ratio.
─────────────────────────────────────────────────────────────────
PCBoard File Ratio Enforcer v2.0 . . . . . . . . . . . . . . . 6
Option C:
--------
This option edits PCBFRE's banking data file. Use this function to
modify information in the banking data file.
1. ║ Name ................. GEOFFREY SY
2. ║ Account balance ...... 200
3. ║ Date withdraw time ... 03-09-92
4. ║ Amount withdrew .... 10
║
5. ║ Date withdraw bytes .. 03-09-92
6. ║ Bytes withdrew ..... 0
║
7. ║ Date of BPM reward ... 03-09-92
8. ║ BPM message pointer .. 4
1. The account holder's name
2. The current time balance
3. Date when time was withdrawn
4. Amount withdrew on that date (item 3)
5. Date when bytes were withdrawn
6. Number of bytes withdrawn on that date (item 5)
6. Date when Bytes/Message reward was given
8. Number of messages the user posted at that point in time.
Step #3:
=======
Setup PCBFRE as a PCBoard Door. Load up PCBSetup, go to edit door
security file and add the following line:
USER DOOR
Filename Password Sec Login SYS SYS Shell Path to DOOR files
════════ ════════ ═══ ═════ ════ ════ ═════ ══════════════════
PCBFRE 0 Y Y N Y
The Autologin and Shell options are optional. If you run more than
one autologin program, you may want to combine all of them into one
script file. PCBFRE requires about 128K to operate. Make sure you
have enough memory if you want PCBoard to shell to PCBFRE. The
USERS.SYS option must be set to Y or PCBFRE won't work!
─────────────────────────────────────────────────────────────────
PCBoard File Ratio Enforcer v2.0 . . . . . . . . . . . . . . . 7
The following is your typical PCBoard door script file. The one
included in this package is named "PCBFRE".
REM Door script for PCBFRE - PCBoard File Ratio Enforcer.
%PCBDRIVE%
CD \PCB\FRE
PCBFRE PCBFRE.CNF %PCBDRIVE%%PCBDIR% /POSTDL /NEW:204800:1:1
CD %PCBDIR%
IF (%INPCB%)==(Y) EXIT
BOARD
Here's the explanation of PCBFRE's command line:
PCBFRE PCBFRE.CNF C:\PCB /POSTDL /NEW:204800:1:1
│ │ │ │
│ │ │ └─┤ Award new user with
│ │ │ │ starting bytes, files,
│ │ │ │ and messages
│ │ │
│ │ └─────────┤ Enforce post/download
│ │ │ instead of post/call
│ │
│ └──────────────┤ Location of your PCBoard
│ │ Node directory
│
└────────────────────────┤ Pathname of PCBFRE's
│ configuration file
The first two (2) options on the command are a must, the rest are
optional.
Available command line options:
/STRICT - This option tells PCBFRE to enforce strict ratios.
Normally a user does not consider exceeded his
post/calls ratios unless he downloads. With the
strict rule in effect, downloads are not used when
determining post/calls ratio. This will mean if the
user uploaded nothing and/or posted no messages, he
is considered exceeding his post/calls and files
ratios.
/POSTDL - This tells PCBFRE to enforce "Messages Post/Files
Download" Ratio instead of the normal Messages
Post/Calls Ratio.
/$$LOGOFF - This tells PCBFRE to run your $$LOGOFF.BAT file
before clearing out the PCBOARD.SYS when a user logs
off inside the bank.
─────────────────────────────────────────────────────────────────
PCBoard File Ratio Enforcer v2.0 . . . . . . . . . . . . . . . 8
/NEW:204800:1:1 - This tells PCBFRE to give new users some
│ │ │ upload credits.
│ │ │
│ │ └──────────────────┤ The number of message
│ │ │ posts to give new users
│ │
│ └────────────────────┤ The number of uploaded
│ │ files to give new users
│
└────────────────────────┤ The number of uploaded
│ bytes to give new users
New users affected by the /NEW option must meet the following
criteria:
Files Uploaded and Downloaded = 0
Bytes Uploaded and Downloaded = 0
User's security level must exist in PCBFRE's ratio table
That's all that's needed. The line "IF (%INPCB%)==(Y) EXIT" is
used to exit from shelled doors. If you don't run PCBFRE as a
shelled door then you may remove it.
Step #4:
========
TRIAL RUN. If you have a runtime error please check the runtime
error codes in this document.
Step #5:
========
FRETEXT contains 2 lines of text. The first line is displayed when
a new user is awarded "Start-Up" bytes/files. The second line is
displayed when a user receives "Bytes Per Message" reward. You may
use the macro %\FILE to display external text files. In addition to
the macros listed on the next page, the following macros are also
available:
Available when "Bytes Per Message" are awarded:
@BPMREWARD@ Bytes rewarded for new messages posted
@BPMPOSTS@ Messages posted qualified for BPM reward
Available when new user "Start-Up" bytes are awarded:
@NEWBYTES@ New users bytes awarded
@NEWFILES@ New users files awarded
@NEWMSGS@ New users messages awarded
─────────────────────────────────────────────────────────────────
PCBoard File Ratio Enforcer v2.0 . . . . . . . . . . . . . . . 9
All external display files may be edited to your own taste to match
the theme of your BBS. See below (PROGRAM CAPABILITIES) if you want
to create language-specific or security-level-specific displays.
From FRESM, press F2 to edit the non-colored version and F3 to edit
the ANSI version. All ASCII, ANSI and IBM graphics characters are
supported in the display files. You can use all PCBoard's @X##
colour codes as well as the following variables:
@MSGRATIO@ SysOp set # of calls allowed per post
@FILERATIO@ SysOp set # of files download per upload
@BYTERATIO@ SysOp set # of bytes download per upload
@ADJBYTES@ Adjusted download bytes available
@MSGLEFT@ Messages user has left/uploaded to PCBoard
@MSGREAD@ Message user has read/downloaded from PCBoard
@BPMBYTES@ Bytes per message in the ratio table
@EARNEDBYTES@ The maximum bytes the user has earned
@EARNEDFILES@ Tiles earned - the number of files the user may
download before exceeding Files UL/DL ratio
@EARNEDMSGS@ Messages earned - the number of downloads or
calls the user may make before exceeding the
Post/Call or Post/Download ratios
@TIMEBAL@ Bank time balance
@MAXTBAL@ Bank maximum balance allowed by SysOp
@TIMEAVAIL@ Bank time available for withdrawal
@MAXTAVAIL@ Bank maximum daily limit allowed by SysOp
@BYTESAVAIL@ Bank bytes available for withdrawal
@MAXBAVAIL@ Bank maximum daily limit allowed by SysOp
$B$ modem open baud rate
$C$ connect bps same as @BPS@
$CLREOL$ clear to end of line
$DEFAULT$ the default color
$N$ port number 0=local, 1..4
$NODE$ current node number
$NONSTOP$ display the rest of the file non-stop
$SYSOP$ sysop name
$TIME$ daily time limit in minutes
@BEEP@ beep speaker, control-g
@BOARDNAME@ the name of your BBS
@BPS@ estimated connect bps
@CITY@ city and state of caller (all caps)
@CLS@ clear screen
@DATAPHONE@ caller's business/data phone number
@DLBYTES@ total bytes downloaded - all calls
@DLFILES@ total files downloaded - all calls
@EVENT@ time of next scheduled event
@EXPDATE@ subscription expiration date
@FIRST@ first name of the user
@HOMEPHONE@ caller voice phone number
@LASTDATEON@ last date on (mm-dd-yy format)
@LASTTIMEON@ last time on (hh:mm format)
─────────────────────────────────────────────────────────────────
PCBoard File Ratio Enforcer v2.0 . . . . . . . . . . . . . . . 10
@NUMTIMESON@ number of times on system
@SECURITY@ users current security level incl. conf. add.
@SYSDATE@ host date in (mm-dd-yy format)
@SYSTIME@ host system in (hh:mm format)
@TIMELEFT@ time remaining that call incl. all credits
@TIMELIMIT@ time allowed from PWRD file
@TIMEUSED@ minutes used since logon
@UPBYTES@ total bytes uploaded - all calls
@UPFILES@ total files uploaded - all calls
@USER@ complete name of the caller
@WAIT@ force a "press enter to continue" prompt
─────────────────────────────────────────────────────────────────
PCBoard File Ratio Enforcer v2.0 . . . . . . . . . . . . . . . 11
┌────────────────────────────────────────────────────────────────┐
│ BANKING FEATURE │
└────────────────────────────────────────────────────────────────┘
If you want to activate the banking feature, just create a separate
door script and use the /BANK switch on the command line. The
sample door script for the bank is included in the archive as BANK.
The content of the script follows:
@ECHO OFF
rem PCBFRE - PCBoard File Ratio Enforcer - BANKING FUNCTIONS
%PCBDRIVE%
CD \DOORS\PCBFRE
PCBFRE PCBFRE.CNF %PCBDIR% /BANK
CD %PCBDIR%
IF (%INPCB%)==(Y) EXIT
BOARD
The time bank feature in PCBFRE is just your ordinary time bank
system, it allows deposits and withdraws.
The bytes bank is unique. It was designed to encourage uploads,
instead of allowing users to stockpile their bytes left-over from
their daily limits. With this banking system, the more the users
upload the more bytes they'll have to withdraw.
For users with bytes ratios not enforced, when bytes are withdrawn,
the amount equal to the user's ratio is taken from the user's total
upload to increase the user's bytes available for the day. These
users' bank ratio is determined by the last security level read.
The security levels are sorted in descending order, so the last
level read would be the lowest level. Since the lowest level
allowed is 0, you may use that to determine the bank bytes ratio
for those users.
For example: A user with a 4:1 bank ratio withdraws 100K from the
bank. This is how the 100K would be calculated:
Each upload byte is worth 4 download bytes, so 100K download
bytes would require 25K upload bytes.
100K / 4 = 25K
25K is then subtracted from the total upload and 100K is
added to the bytes available.
For users with bytes ratios enforced, the bank will calculate the
proper amount they may withdraw without exceeding their ratios.
─────────────────────────────────────────────────────────────────
PCBoard File Ratio Enforcer v2.0 . . . . . . . . . . . . . . . 12
┌────────────────────────────────────────────────────────────────┐
│ PROGRAM CAPABILITIES │
└────────────────────────────────────────────────────────────────┘
PCBFRE is a standard ProKit door. Some of its features include:
+ Security-level / Language specific display files:
To activate this feature, replace the first 3 letters of
the menu name with the security level.
For level 60, NORMAL becomes 060MAL
For language specific menu, let say French just add the
extension as specified in PCBoard.
For French (.FRE), NORMAL becomes NORMAL.FRE
Add level specific and it becomes 060MAL.FRE
+ Support for non-standard COM ports COM3 - COM8. If the
door doesn't work with your COM port you may set the
following environment variables:
SET COMBASE=nnnn
Sets the base I/O address (in DECIMAL) for non-standard
COM ports.
SET COMIRQ=n
Sets the IRQ level for non-standard COM ports.
+ Full Multi-Node support.
+ Support for Baud Rates up to 115200 bps.
+ Complete session logging. Everything the user sees can be
captured in a session log. This is enabled by adding
SET PRODEBUG=ON
to the door script; output will be logged to DEBUG.OUT.
+ Operation under DoubleDOS, TaskView or DesqView is fully
supported. The door will give up idle time to speed the
other partition. If screen bleedthrough or background
lockups occur, you may need to add the environment
statement
SET OVCRT=ON
before executing the door. This disables direct screen
write.
+ Automatic network file sharing is implemented on all
system files. The door has been tested under LanTastic,
Novell, NTNX and other true networks.
─────────────────────────────────────────────────────────────────
PCBoard File Ratio Enforcer v2.0 . . . . . . . . . . . . . . . 13
+ Sysop function keys supported are:
F2 .... Lockout current user
F3 .... Toggle printer logging
F4 .... Toggle operator page bell
F5 .... Shell to DOS while caller is online
F7 .... Toggle alarm beeps
F8 .... Force immediate logoff and hangup
F9 .... Toggle local display
F10 . .. Chat with user
ALT-B .. Debug/display memory and overlay information
ALT-I .. File input during message entry and CHAT
ALT-F .. File capture of all displays
ALT-M .. Node status display
ALT-N .. Sysop on-next
ALT-P .. Print complete session
ALT-X .. Sysop dos-exit next
UP ... Increase online time
DOWN ... Decrease online time
PgUp ... Display comments from user file
PgDn ... Display phone numbers, password
HOME ... Listing available functions
SHIFT .. F1..F10 . Sysop macro keys defined in PCBSETUP
┌────────────────────────────────────────────────────────────────┐
│ ERROR CODES │
└────────────────────────────────────────────────────────────────┘
Error Class Description
2 DOS: File not found (Check command line)
3 DOS: Path not found
4 DOS: Too many open files (Check CONFIG.SYS)
5 DOS: File access denied
6 DOS: Bad file handle
12 DOS: Bad file access code
16 DOS: Can't remove current dir
15 DOS: Bad drive number
100 I/O: Disk read error
101 I/O: Disk write error
102 I/O: File not assigned
103 I/O: File not open
104 I/O: File not open for input
105 I/O: File not open for output
106 I/O: Bad numeric format (Check numbers in .CNF)
150 CRITICAL: Disk is write-protected
151 CRITICAL: Unknown unit
152 CRITICAL: Drive not ready
153 CRITICAL: Unknown command
154 CRITICAL: CRC error in data
─────────────────────────────────────────────────────────────────
PCBoard File Ratio Enforcer v2.0 . . . . . . . . . . . . . . . 14
156 CRITICAL: Disk seek error
157 CRITICAL: Unknown media type
158 CRITICAL: Sector not found
159 CRITICAL: Printer out of paper
160 CRITICAL: Device write fault
161 CRITICAL: Device read fault
162 CRITICAL: Network or Hardware failure
200 FATAL: Division by zero
201 FATAL: Range check
202 FATAL: Stack overflow
203 FATAL: Heap overflow
204 FATAL: Bad pointer operation
205 FATAL: Floating point overflow
206 FATAL: Floating point underflow
207 FATAL: Bad floating point operation. Check to
make sure all the numeric values in the
PCBFRE security table are of reasonable
value. Large numbers and negative numbers
will cause this error.
208 FATAL: Overlay Manager not initialized
┌────────────────────────────────────────────────────────────────┐
│ PROBLEM REPORTS │
└────────────────────────────────────────────────────────────────┘
If you need to report a problem, please capture the session using
DOS environment variable "SET PRODEBUG=ON". The ouput file called
"DEBUG.OUT" will be in the same directory that PCBFRE is executed
from. Depending on the node, the file will be named "DEBUG#.OUT"
where # is the node number. Please include this file as well as
the USERS.SYS file in use during that session and a thorough
explanation of the problem encountered. Please ZIP these files up
and send it to my support BBS.
─────────────────────────────────────────────────────────────────
PCBoard File Ratio Enforcer v2.0 . . . . . . . . . . . . . . . 15
┌────────────────────────────────────────────────────────────────┐
│ SUPPORT/REGISTRATION │
└────────────────────────────────────────────────────────────────┘
If you have any questions, bugs, comments or suggestions, please
contact me. I may be reached on the PCBoard conference on NANet,
City2City(tm), Intelec(tm), and other networks. I can also be reach
on my support BBS or by snail-mail to the above address. Registered
users may contact me using the voice number in the registration
document.
Since this is user supported software, I don't expect you to
register if you don't like it or if it doesn't meet your needs.
Just stop using it after a reasonable trial period (2-3 weeks). The
program is not crippled in any way, there is only a short delay at
the start/exit of the program to remind the user that the copy is
un-registered.
If you like the program and use it regularly, please register it.
The registration cost is a one-time fee of $20.00. With the
registration you'll receive unlimited voice support and upgrades.
Your registration encourages further development, enhancement and
my continued support of the product. Please send your registration
in the form of a Money Order, Personal Cheque, or Cashier's Cheque
to the above address.
┌────────────────────────────────────────────────────────────────┐
│ REGISTRATION OPTIONS │
└────────────────────────────────────────────────────────────────┘
1 - Your registration information will be left in a message
on my support BBS. You'll need to scan conference 3 for
it.
2 - I'll upload the latest copy with the registration
information to your BBS. If you're long distance, please
add appropriate cost to cover a long-distance call.
3 - You'll receive the latest version on a disk by
snail-mail. Please add appropriate costs to cover disk
and mailing cost.
4 - I'll send your registration information in a first class
letter. No additional cost is required.
5 - You may drop by my home to pick up the registration.
Please let me know in advance. I live in a rough
neighborhood, so watch yourself if you really must pick
up the registration in person. A few has dropped by so
far and have escaped safely with their registrations.
─────────────────────────────────────────────────────────────────
PCBoard File Ratio Enforcer v2.0 . . . . . . . . . . . . . . . 16
┌────────────────────────────────────────────────────────────────┐
│ CREDITS │
└────────────────────────────────────────────────────────────────┘
Thanks to Jeff Leung:
For the great job of providing his time and resources on The
GRAFIX Connection to support PCBFRE and my other programming
efforts. I'd also like to thank him waking me up at 4:00 am in
the morning everytime he thought he had found a bug in PCBFRE.
Thanks to Stew Francis, Shaun Gallant, Kerry Kostner, Terry Wilson,
Dennis Kaczor, Leonard Lada:
For all the ideas, suggestions, bug reports, and beta testing
during the beta cycle. Without the help of these individuals,
I wouldn't have been able to find and squash those nasty
little bugs running loose inside PCBFRE. Thanks guys, for the
help, patience, and support.
Thanks to all registered users of PCBFRE for the continued support.
Without such support, PCBFRE wouldn't be where it is today.
┌────────────────────────────────────────────────────────────────┐
│ STANDARD DISCLAIMERS/COPYRIGHTS │
└────────────────────────────────────────────────────────────────┘
This program is provided on an "AS IS" basis. No warranty of any
kind is expressed or implied. YOU USE THIS PROGRAM AT YOUR OWN
RISK. I take no responsibility for any damage caused directly or
indirectly from the use or the inability to use this program.
ProKit & Pro* Utilities - Copyrighted: Samuel Smith - The Tool Shop
PCBoard - Copyrighted: Clarke Development Company
Other - Copyrighted: Respected Owners
─────────────────────────────────────────────────────────────────
PCBoard File Ratio Enforcer v2.0 . . . . . . . . . . . . . . . 17
